Automated dynamic document generator

ABSTRACT

A method for automated dynamic document generation includes: storing, in a memory of a document generator, (i) a common pool of objects each defining document content and having respective object identifiers, (ii) a plurality of templates having respective template identifiers and containing respective template subsets of the object identifiers, and (iii) a plurality of master templates having respective master template identifiers and containing respective master template subsets of the object identifiers; establishing a connection to a data source; detecting document initiation data in the data source including a selected one of the template identifiers; responsive to the detection, retrieving a selected one of the master template identifiers associated with the selected template identifier; retrieving the template subset and the master template subset of objects corresponding to the selected template identifier and the selected master template identifier; and generating a document according to the template subset and the master template subset.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/633,871, which claims priority from U.S. Provisional PatentApplication No. 62/536,563, filed Jul. 25, 2017. The contents of theabove-referenced documents are incorporated herein by reference.

FIELD

The specification relates generally to document generation, andspecifically to a method, system and apparatus for automatically anddynamically generating documents.

BACKGROUND

Systems of various types can be configured to generate documents, e.g.for delivery to entities external to the system. Certain documentcontent may appear in a number of different document types, which maylead to inefficient use of storage components, as well as inconsistentgeneration of such shared content.

SUMMARY

An aspect of the specification provides a method in a computing devicefor automated dynamic document generation, comprising: storing, in amemory of a document generator, (i) a common pool of objects eachdefining document content and having respective object identifiers, (ii)a plurality of templates having respective template identifiers andcontaining respective template subsets of the object identifiers, and(iii) a plurality of master templates having respective master templateidentifiers and containing respective master template subsets of theobject identifiers; at the document generator, establishing a connectionto a data source; at the document generator, detecting documentinitiation data in the data source including a selected one of thetemplate identifiers; responsive to the detection, retrieving a selectedone of the master template identifiers associated with the selectedtemplate identifier; retrieving the template subset and the mastertemplate subset of objects corresponding to the selected templateidentifier and the selected master template identifier; and generating adocument according to the template subset and the master template subsetof objects.

BRIEF DESCRIPTIONS OF THE DRAWINGS

Embodiments are described with reference to the following figures, inwhich:

FIG. 1 depicts a system for automated dynamic document generation;

FIG. 2 depicts a method of automated dynamic document generation in thesystem of FIG. 1 , according to a non-limiting embodiment;

FIGS. 3A, 3B, and 4 depict the determination of data variables forretrieval during performance of the method of FIG. 2 ;

FIG. 5 depicts the retrieval of data from database by the processingserver of system of FIG. 1 ;

FIG. 6 depicts an email showcasing the resulting generated dynamicallygenerated document as part of performance of the method of FIG. 2 ; and

FIG. 7 depicts the distribution of the dynamically generated document toclient devices of system of FIG. 1 .

DETAILED DESCRIPTION OF THE EMBODIMENTS

FIG. 1 depicts a system 100 for automated dynamic document generation.System 100 comprises a processing server 104, and a database server 140.Processing server 104 and database server 140 are coupled to at leastone client device 170. In the present embodiment, a plurality of clientdevices 170-1, 170-2 . . . 170-q are shown. Client devices 170 arereferred herein generically as a client device 170 and collectively asclient devices 170. This nomenclature is used elsewhere herein. Eachclient device 170 can be any of a cellular phone, a smart phone, atablet computer, a desktop computer, a laptop computer, smarttelevision, gaming console, virtual reality computing device, and thelike.

Processing server 104 is connected to network 160 via data link 106.Database server 140 is connected to network 160 via data link 142. Inturn, network 160 is connected to client devices via data links 172-1,172-2, . . . 172-q. A person skilled in the art will recognize that datalink 106, data link 142 and data links 172 are not particularly limitedin their configuration and can be any one of, or any suitablecombination of wired and wireless links. Network 160 can be any suitablecombination of wired and wireless networks, including but not limited toa Wide Area Network (WAN) such as the Internet, a Local Area Network(LAN) such as a corporate data network, WiFi networks, cell phonenetworks (e.g. LTE) and the like.

As will be described in detail below, database server 140 provides adatabase 156 from which processing server 104 can retrieve data togenerate documents. Processing server 104 operates to generate documentsand to distribute the documents to respective client devices 170 to bedisplayed.

Processing server 104 includes a central processing unit (CPU) 108, alsoreferred to herein as processor 108, interconnected with a memory 116.Memory 116 stores computer readable instructions executable by processor108, including a document preparation application 120, at least onebehavioral schema 132, at least one master template schema 124 and atleast one template schema 128 all of which will be discussed in greaterdetail further below. Processor 108 and memory 116 are generallycomprised of one or more integrated circuits (ICs) and can have avariety of structures, as will now occur to those skilled in the art(for example, more than one CPU can be provided). Processing server 104also includes a communications interface 112 interconnected withprocessor 108. Communications interface 112 thus includes the necessaryhardware, such as radio transmitter/receiver units, network interfacecontrollers and the like, to communicate over link 106.

Master template schemas 124 each have master template identifiers toallow document preparation application 120 to identify and retrieve thecorresponding master template schema 124 from processing server 104.Template schemas 128 also each have template identifiers to allowdocument preparation application 120 to identify and retrievecorresponding template schema 128 from processing server 104. Mastertemplate identifiers and template identifiers will be discussed ingreater detail further below.

Processing server 104 executes the instructions of document preparationapplication 120 to perform, in conjunction with the other components ofprocessing server 104, various functions related to the generation ofdocuments to be sent to client devices 170. In the discussion below ofthose functions, it will be understood that processing server 104 is soconfigured via the processing of the instructions in documentpreparation application 120 by the hardware components of processingserver 104 (including processor 108 and memory 116).

Database server 140 includes a central processing unit (CPU) 144, alsoreferred to herein as processor 144, interconnected with a memory 152.Processor 144 and memory 152 are generally comprised of one or moreintegrated circuits (ICs), and can have a variety of structures, as willnow occur to those skilled in the art (for example, more than one CPUcan be provided).

Memory 152 stores database 156. In the present embodiment, database 156is an electronic legal records database 156 containing case filesrepresenting government registrable intellectual property rights (IPR)from any suitable jurisdiction or combination of jurisdictions. IPRsinclude, without limitation, patents, trademarks, industrial designs,utility models and copyrights. In the present embodiment, the electroniclegal records database is also a workflow engine that keeps track ofdeadlines of subsequent tasks within each case. In another version,database 156 can be electronic accounting records containing case filesrepresenting general ledgers comprised of transactions.

Each case within database 156 has a unique identifier. In the presentembodiment of an electronic legal records database, the uniqueidentifier is a case reference number. A case reference corresponds to aspecific electronic legal record in database 156. For example, a casereference can be an application number for a patent application that hasbeen filed at the United States Patent and Trademark Office (USPTO).Another example of a case reference can be the attorney docket filenumber such as those commonly employed in filing systems of law firms.

In the present embodiment, examples of data variables within anelectronic legal records database include, without limitation, dates(e.g. records of previous events), deadlines (e.g. dates of futureevents be completed), names of inventors, applicants, and other partiesto the case. A person skilled in the art will now recognize otherexamples of data variables that are associated with unique casereference identifiers.

Database server 140 also includes a communications interface 148interconnected with processor 144. Communications interface 148 thusincludes the necessary hardware, such as radio transmitter/receiverunits, network interface controllers and the like, to communicate overlink 142.

Although database server 140 and processing server 104 are discussedbelow as two distinct servers, in some embodiments they can beimplemented in a single server, or in a greater number of servers thantwo.

Client devices 170 includes respective central processing units (CPU)174-1, 174-2, . . . 174-q, also referred to herein as processors 174,interconnected with respective memories 182-1, 182-2, . . . 182-q.Processor 174 and memory 182 are generally comprised of one or moreintegrated circuits (ICs), and can have a variety of structures, as willnow occur to those skilled in the art (for example, more than one CPUcan be provided). Client devices 170 also includes respectivecommunications interfaces 178-1, 178-2, . . . 178-q interconnected withrespective processors 174. Communications interface 178 thus includesthe necessary hardware, such as radio transmitter/receiver units,network interface controllers and the like, to communicate over link172.

Referring now to FIG. 2 , a method 200 of automated dynamic documentgeneration is illustrated. Method 200 will be described in conjunctionwith its performance by system 100. Specifically, method 200 isperformed by processing server 104 via the execution of documentpreparation application 120.

Beginning at block 205, processing server 104 queries database 156periodically for new data and detects document initiation data whenavailable on database 156. In other embodiments, processing server 104can query database 156 on a fixed schedule (e.g. 2:00 PM every day), oran application on database server 140 can create a queue of cases withdocument initiation data, which is retrieved periodically by processingserver 104. Document initiation data includes at least a templateidentifier and a case reference number. As will be further discussedbelow in block 210, document preparation application 120 uses thetemplate identifier to retrieve a corresponding template schema 128, andsubsequently to determine the master template schema 124, and uses thecase reference number to retrieve relevant case data from the database156. In the present embodiment, document initiation data is generated aspart of the workflow engine within database 156. For example, thereceipt of a patent filing receipt from the USPTO will trigger theworkflow engine to produce documentation initiation data for a reportingletter to the client (one of the parties on the case). The documentinitiation data includes the case reference number pertaining to theUSPTO filing receipt and the template identifier for a reporting letterregarding the receipt of a USPTO filing receipt.

At block 210, document preparation application 120 on processing server104 retrieves a master template identifier based on the correspondingtemplate identifier retrieved in the document initiation data. Documentpreparation application 120 can identify the associated master templateidentifier at block 210 based on the template identifier retrieved atblock 205 via a database table residing on database 156. The databasetable residing on database 156 has a list of each child templateidentifier and its corresponding parent master template identifier. Inanother embodiment, the database table with the corresponding parentmaster template identifiers and child template identifiers can reside ona database on processing server 104.

Within the database table, each master template identifier is associatedto at least one template identifier. More specifically, each templateidentifier is associated to a parent master template identifier. Table 1illustrates an example of the database table.

TABLE 1 Master Template Identifier to Template Identifier RelationshipMaster Template Identifier Template Identifier Reporting LetterReporting the receipt of a USPTO Filing Receipt Reporting LetterReporting the filing of a response to a patent office action with theUSPTO Reminder Letter Reminding client to provide instructions onresponse to a patent office action Reminder Letter Reminding client toprovide instructions on payment of maintenance fees

In the example above, where parent master template identifier isreporting letter master template identifier, then the children templateidentifiers are all event specific reporting letters, such as areporting letter regarding the receipt of a USPTO filing receipt, or areporting letter regarding the filing of a response to a patent officeaction with the USPTO. In another example, where the patent mastertemplate identifier is reminder letter master template identifier, thenthe children template identifiers are all event specific reminderletters, such as a reminder to provide instructions on the response to apatent office action, or a reminder to provide instructions on whetherto pay maintenance fees on a case. A person skilled in the art will nowbe able to recognize the different combinations and sets of templateidentifiers and the corresponding master template identifiers.

At block 215, document preparation application 120 retrieves datavariables from database server 140 for population into the proposedgenerated document. Document preparation application 120 determines theappropriate data variables to retrieve based on master template schema124.

FIG. 3A illustrates an example of a master template schema 124. Mastertemplate schema 124 is comprised of lines of programmed instructions,each instructing the document preparation application 120 to retrieveone or more objects, either from the common pool, or from templateschema 128. Template schemas 128 are identified via template identifiersand are repositories of objects that are template specific. Objects aresections of text that can contain data variables to be retrieved bydocument preparation application 120 from database 156 as instructed bymaster template schemas 124, and are either retrieved from a common poolof objects or from template schema 128. Objects that are within thecommon pool can be used by different master template schemas, whereasobjects within template schema 128 are template specific.

In the present embodiment, example master template schema 124 representsa reporting letter to a client. In this example, master template schema124 was determined based on a corresponding template identifier for thereporting of the filing of a response of a patent office action with theUSPTO. Programmed instructions 310 is instructing document preparationapplication 120 to retrieve an object named “what_happened” from withinthe reporting of the filing of a response of a patent office action withthe USPTO template schema 128 (i.e. the template schema 128corresponding to the template schema identifier retrieved at block 205;in other words, the specific object retrieved as a result of theinstructions 310 depends on the template identifier retrieved at block205). Document preparation application 120 is configured to retrieve theobject from within template schema 128 based on the template identifierfrom block 205 and the “T” prefix, which will be further discussedbelow. The corresponding “what_happened” template specific object is asshown in object 410. Similarly programmed instructions 315 isinstructing document preparation application 120 to retrieve an objectnamed “what_happens_next” from within the same reporting of the filingof a response to a patent office action with the USPTO template schema128.

Programmed instructions 305 is instructing document preparationapplication 120 to conditionally retrieve an object named “obj_header”if present within template schema 124, and if not present, to retrievethe object from the common pool of objects. This behavior is based offof the “TMT” prefix.

In the present embodiment, programmed instructions contain prefixes,such as “TMT” within programmed instruction 305, and “T” withinprogrammed instruction 310 and 315. Prefixes within programmedinstructions 305, 310 and 315 instruct document preparation application120 whether to allow for conditional behavior within master templateschema 124. Conditional behavior is not limited to master templateschemas 124, but can be used within template schemas 128 and objects.

In the present embodiment, programmed instruction 310 and 315 with theprefix “T” instructs the document preparation application 120 that thereis no conditional behavior, and that document preparation application120 should retrieve the object directly from the corresponding templateschema 128.

Referring now to FIG. 3B, in the example containing “TMT”, the object“obj_header” can be overridden by a template specific object named“obj_header”. At block 355, the programmed instructions within mastertemplate schema 124 begin the process of determining whether a templatespecific object is used, or whether an object from the common pool isused. At block 360, document preparation application 120 determines ifthe specific template schema 128 has a template specific object named“obj_header”. If it does, then at block 365, document preparationapplication 120 uses the template specific object. If at block 360,there is no template specific object named “obj_header”, then thedocument preparation application will default back to the common poolfor the object name “obj_header” at block 370.

Referring back to FIG. 3A, programmed instruction 320 contains theprefix “CTMT”, which instructs document preparation application 120 toconditionally retrieve an object from the common pool based on a flagwithin database 156. In the present embodiment, an object is displayedif there is a flag on the case within database 156, showing that theclient has paid up front for services. A person skilled in the art willnow recognize the combinations allowing for document preparation 120 toretrieve template specific objects from template schema 128, or toretrieve objects from a common pool to be used within master templateschema 124 or other embodiments of conditionally retrieving objects fromeither template schema 128 or a common pool of objects.

A person skilled in the art will also now recognize the variations andcombinations on programmed instructions within master template schema124 in generating a document.

FIG. 4 illustrates an example of a partially generated document based onmaster template schema 124, after document preparation application 120has retrieved template schema 128 for reporting the filing of a responseto a patent office action with the USPTO, and the respective objectsfrom the common pool of objects. Object 405 corresponds to programmedinstructions 305, and depicts the header text as part of the headerobject. In the present embodiment, the header object is an object fromthe common pool and as such, can be used by multiple master templateschemas 124. Object 410 corresponds to programmed instructions 310, anddepicts the template specific text associated with template identifierfor reporting the filing of a response to a patent office action withthe USPTO. A person skilled in the art will now be able to recognizedifferent objects and template schemas, the architectural relationshipbetween master template schemas 124, template schemas 128, and objects,and how document preparation application 120 is instructed to create thestructure of the document.

Data fields 415, 420 and 425 each represent data variables that documentpreparation application 120 is instructed to retrieve from database 156by corresponding objects (object 405 instructs data field 415 and 420,and object 410 instructs data field 425). Data variables can beprogrammed on different schemas, including, but not limited to, mastertemplate schema 124, template schema 128, and on objects. In the presentembodiment, data field 415 is instructing the document preparationapplication 120 to retrieve the attorney docket number from database156. Data field 420 is instructing document preparation application 120to retrieve the title of the patent from database 156. Data field 425 isinstructing the document preparation application 120 to retrieve thedeadline to respond to the patent office action to the USPTO fromdatabase 156. Data fields 415, 420, and 425 are examples of datavariables that need to be retrieved in the present embodiment depictedin schema 400, and a person skilled in the art will now be able torecognize that schema 400 contains other data variables that need to beretrieved from database 156. A person skilled in the art will also nowbe able to recognize the different data variables that can be used, andtheir association to master template schemas 124, template schemas 128and objects.

Returning to FIG. 2 , at block 215, document preparation application 120on processing server 104 retrieves the data variables prescribed bymaster template schema 124, and objects from either the common pool orfrom template schema 128, from database 156 on database server 140. Theretrieval of the data variables are based on a single record indatabase, based on the case reference number, which is part of thedocument initiation data that was received by document preparationapplication 120.

FIG. 5 is an example of the retrieval of data variables. For example, ifthe case reference number that accompanied the data initiation data wasan application number 2253200 for a patent filed with the USPTO, thendocument preparation application 120 will retrieve data variablesspecific to that case within electronic legal records database 156.

Returning to FIG. 2 , at block 220, document preparation application 120generates the document. Document generation is performed based on mastertemplate schema 124, template schema 128, objects and the retrieved datavariables from database 156. Document preparation application 120 willalso use instructions as provided by behavioral schema 132 in generatingthe document. At block 225, the generated document is distributed toclient device 170.

Behavioral schema 132 is a blueprint that instructs document preparationapplication 120 on the behavioral characteristics of documentgeneration. For example, behavioral schema 132 can instruct documentpreparation application 120 to generate the document in hypertext markuplanguage (HTML) file format, and to email the document as part of anemail message to client addresses that are retrieved from database 156,to be displayed on client device 170. In another example, behavioralschema 132 can instruct document preparation application 120 to generatethe document in a portable document format (PDF) file and upload it toclient device 170 to be viewed by a third-party software. A personskilled in the art will now be able to recognize the different possiblecombinations and sets of characteristics that behavioral schema 132 canbe comprised of.

Referring to FIG. 6 , display 600 is an example of a generated documentthat has been distributed to client device 170 and is being displayed asan email on client device 170. In present embodiment, documentpreparation application 120 prepared the reporting of the filing of aresponse to a patent office action at the USPTO with the accompanyingbehavioral schema 132 of generating the document as an HTML file, andemailed it to client device 170 as part of the body of the emailmessage.

Data fields 620 and 625 are examples of the data variables that documentpreparation application 120 retrieved from database 156 and generated aspart of the document. Data field 620 corresponds to data field 420 fromFIG. 4 , and data field 625 corresponds to data field 425 from FIG. 4 .A person skilled in the art should now be able to recognize the use ofdata variables throughout method 200 by document preparation application120.

FIG. 7 is an example of the generation and distribution of the document.In the present embodiment, the document is a letter reporting the filingof a response to an office action to the USPTO, and is generated bydocument preparation application 120 using master template schema 124*,template schema 128* and follows instructions within behavioral schema132*. The finalized generated document is then distributed to the clientdevice 170 based on instructions from behavioral schema 132. A personskilled in the art will now be able to recognize the differentcombinations and sets of master template schemas 124, template schemas128 and behavioral schemas 132 that allow for different variations ofautomated dynamic document generation using method 200 in system 100.

Those skilled in the art will appreciate that in some embodiments, thefunctionality of any one or more of the applications 120 may beimplemented using pre-programmed hardware or firmware elements (e.g.,application specific integrated circuits (ASICs), electrically erasableprogrammable read-only memories (EEPROMs), etc.), or other relatedcomponents.

The scope of the claims should not be limited by the embodiments setforth in the above examples, but should be given the broadestinterpretation consistent with the description as a whole.

The invention claimed is:
 1. A method for document generation in acomputing device, comprising: storing, in a memory: (i) a common pool ofobjects having respective object identifiers, (ii) a plurality oftemplates having respective template identifiers, each templatecontaining, for each of a subset of the object identifiers, a localdefinition of a corresponding object from the common pool, and (iii) aplurality of master templates having respective master templateidentifiers, each master template containing, for each of a furthersubset of the object identifiers, an associated string defining objectretrieval behavior for the object identifier; establishing a connectionto a data source; detecting, via the connection, initiation dataincluding an active template identifier; responsive to the detection,retrieving an active master template identifier associated with theactive template identifier; for each of the further subset of objectidentifiers of the master template corresponding to the active mastertemplate identifier, retrieving an object from a source selected fromeither the common pool or a template corresponding to the activetemplate identifier, according to the string; and generating a documentaccording to the retrieved objects.
 2. The method of claim 1, herein atleast one of the common pool of objects defines static document content.3. The method of claim 1, wherein at least one of the common pool ofobjects defines dynamic document content.
 4. The method of claim 3,wherein the dynamic document content includes a reference to the datasource.
 5. The method of claim 1, further comprising: storing, in thememory, a mapping of template identifiers to master templateidentifiers; wherein retrieving the active master template identifierincludes retrieving the active master template identifier from themapping according to the active template identifier.
 6. The method ofclaim 1, further comprising storing behavioral data defining at leastone of a format for the document and a transmission mechanism for thedocument.
 7. The method of claim 6, further comprising: responsive togenerating the document, transmitting the document according to thetransmission mechanism.
 8. A computing device, comprising: a memorystoring; (i) a common pool of objects having respective objectidentifiers, (ii) a plurality of templates having respective templateidentifiers, each template containing, for each of a subset of theobject identifiers, a local definition of a corresponding object fromthe common pool, and (iii) a plurality of master templates havingrespective master template identifiers, each master template containing,for each of a further subset of the object identifiers, an associatedstring defining object retrieval behavior for the object identifier; aprocessor interconnected with the memory, the processor configured to:establish a connection to a data source; detect, via the connection,initiation data including an active template identifier; responsive tothe detection, retrieve an active master template identifier associatedwith the active template identifier; for each of the further subset ofobject identifiers of the master template corresponding to the activemaster template identifier, retrieve an object from a source selectedfrom either the common pool or a template corresponding to the activetemplate identifier, according to the string; and generate a documentaccording to the retrieved objects.
 9. The computing device of claim 8,wherein at least one of the common pool of objects defines staticdocument content.
 10. The computing device of claim 8, wherein at leastone of the co on pool of objects defines dynamic document content. 11.The computing device of claim 10, wherein the dynamic document contentincludes a reference to the data source.
 12. The computing device ofclaim 8, wherein the memory stores a mapping of template identifiers tomaster template identifiers; and wherein the processor is configured, toretrieve the active master template identifier, to retrieve the activemaster template identifier from the mapping according to the activetemplate identifier.
 13. The computing device of claim 8, wherein thememory stores behavioral data defining at least one of a format for thedocument and a transmission mechanism for the document.
 14. Thecomputing device of claim 13, wherein the processor is furtherconfigured to: responsive to generating the document, transmit thedocument according to the transmission mechanism.
 15. A non-transitorycomputer-readable medium storing a plurality of computer-readableinstructions executable by a processor of a computing device to: store:(i) a common pool of objects having respective object identifiers, (ii)a plurality of templates having respective template identifiers, eachtemplate containing, for each of a subset of object identifiers, a localdefinition of a corresponding object from the common pool, and (iii) aplurality of master templates having respective master templateidentifiers, each master template containing, for each of a furthersubset of the object identifiers, an associated string defining objectretrieval behavior for the object identifier; establish a connection toa data source; detect, via the connection, initiation data including anactive template identifier; responsive to the detection, retrieve anactive master template identifier associated with the active templateidentifier; for each of the further subset of object identifiers of themaster template corresponding to the active master template identifier,retrieve an object having the object identifier in the instruction, froma source selected from either the common pool or a templatecorresponding to the active template identifier, according to thestring; and generate a document according to the retrieved objects. 16.The non-transitory computer-readable medium of claim 15, wherein atleast one of the common pool of objects defines static document content.17. The non-transitory computer-readable medium of claim 15, wherein atleast one of the common pool of objects defines dynamic documentcontent.
 18. The non-transitory computer-readable medium of claim 17,wherein the dynamic document content includes a reference to the datasource.
 19. The non-transitory computer-readable medium of claim 15,wherein the instructions are further executable by the processor to:store a mapping of template identifiers to master template identifiers;in order to retrieve the active master template identifier, retrieve theactive master template identifier from the mapping according to theactive template identifier.
 20. The non-transitory computer-readablemedium of claim 15, wherein the instructions are further executable bythe processor to: store behavioral data defining at least one of aformat for the document and a transmission mechanism for the document;and responsive to generating the document, transmit the documentaccording the transmission mechanism.